Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backend/frontend] Implementation of sensitive configuration protection (#8284) #8509

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

aHenryJard
Copy link
Member

@aHenryJard aHenryJard commented Sep 25, 2024

Proposed changes

  • Add a configuration in Role to know if user is allow or not to change sensitive configuration on the platform

  • Add this configuration in the capability list in the UI

  • Protect initial groups/roles Administrator(s) and Connector(s) from modification when user are not allow to modifiy sensitve configuration

  • Under feature flag

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case (coverage and e2e)
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

Further comments

@github-actions github-actions bot added the filigran team use to identify PR from the Filigran team label Sep 25, 2024
@aHenryJard aHenryJard changed the title Implementation of sensitive configuration protection (#8284) [backend/frontend] Implementation of sensitive configuration protection (#8284) Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
filigran team use to identify PR from the Filigran team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants